ci: Enable -Werror=maybe-uninitialized
authorColin Walters <walters@verbum.org>
Tue, 20 Jun 2017 21:19:01 +0000 (17:19 -0400)
committerAtomic Bot <atomic-devel@projectatomic.io>
Tue, 20 Jun 2017 22:27:18 +0000 (22:27 +0000)
We don't want to inject this warning by default for every build
like the other ones in `configure.ac`, since it can be spruriously
wrong.  But there's no reason not to have a more extended set of
warnings for well-known toolchains (e.g. f25).

Closes: #943
Approved by: jlebon

.papr.yml

index 6946b9365eb9d84d38495d63ef2fef3be914246f..1addf061a10207c1c2893366e701ea55e711889b 100644 (file)
--- a/.papr.yml
+++ b/.papr.yml
@@ -12,7 +12,9 @@ packages:
   - git
 
 env:
-    CFLAGS: '-fsanitize=undefined -fsanitize-undefined-trap-on-error -fsanitize=address -O2 -Wp,-D_FORTIFY_SOURCE=2'
+    # Enable all the sanitizers for this primary build.
+    # We only use -Werror=maybe-uninitialized here with a "fixed" toolchain
+    CFLAGS: '-fsanitize=undefined -fsanitize-undefined-trap-on-error -fsanitize=address -O2 -Wp,-D_FORTIFY_SOURCE=2 -Werror=maybe-uninitialized'
     ASAN_OPTIONS: 'detect_leaks=0'  # Right now we're not fully clean, but this gets us use-after-free etc
     # TODO when we're doing leak checks: G_SLICE: "always-malloc"